Skip to content

spotify, slack, plaid: regenerate plugins for SDKs with fixed OAuth endpoints - #125

Merged
Darker98 merged 1 commit into
mainfrom
fix-oauth-spotify-slack-plaid
Nov 16, 2026
Merged

Darker98 merged 1 commit into
mainfrom
fix-oauth-spotify-slack-plaid

Conversation

@Darker98

Copy link
Copy Markdown
Contributor

Regenerates the Spotify, Slack and Plaid plugins against SDKs whose OAuth endpoints were wrong. All nine SDKs (C#, Python, TypeScript) were regenerated from fixed specs and pushed to main.

The OAuth fixes

Plugin Was Now Spec change (cost)
spotify sign-in and tokens built from the API host: api.spotify.com/v1/authorize, /v1/api/token accounts.spotify.com/authorize, accounts.spotify.com/api/token; API stays on api.spotify.com/v1 removed accounts.spotify.com from servers. The generator had made it a second environment, and it now becomes its own auth server. The SDK loses the meaningless Environment2.
slack legacy oauth.access, and an authorize URL of slack.com/api/authorize (answers unknown_method) v2: slack.com/oauth/v2/authorize, slack.com/api/oauth.v2.access switched authorizationUrl/tokenUrl to v2 and removed slack.com/oauth from servers. The SDK loses Environment2.
plaid api.plaid.com/oauth2/apiv2/token with HTTP Basic /oauth/token on the selected environment (production.plaid.com / sandbox.plaid.com), credentials in the form body tokenUrl corrected; x-oauth2-credentials-placement: body added.

Skill edits on top of the regeneration (Plaid only): Plaid's token endpoint rejects a request without a scope (invalid_scope: scope is required). The examples now set user:write, and the .NET token-URL sentence names the selected environment instead of always production.

SDK commits

Plugin C# Python TypeScript
spotify spotify-csharp-sdk a13fb04 spotify-python-sdk fb34544 spotify-web-api-typescript-sdk d247572
slack slack-csharp-sdk fd68abd slack-python-sdk 6392707 slack-typescript-sdk cb5f703
plaid plaid-csharp-sdk 726db69 plaid-python-sdk 595df19 plaid-typescript-sdk fcc05b3

Each SDK commit also adds the .apimatic/ generation metadata.

Verification

  • Compile: 8/9 pass (dotnet build 0 warnings / 0 errors, strict mypy, npm build + typecheck + lint).
    • plaid-python fails to import: the generator types the multipart field TransferDiligenceDocumentUploadRequest.file as FileResponse, which pydantic cannot model (pydantic 2.11 through 2.14).
    • The previously published plaid-python-sdk fails identically. This is pre-existing and was pushed as-is by decision.
  • Live, Spotify (Python SDK): client-credentials token from accounts.spotify.com/api/token (200), then a catalog call on api.spotify.com/v1 (200). The authorize URL the SDK builds is on accounts.spotify.com/authorize.
  • Live, Slack (Python SDK, no redirect URL available):
    • The v2 authorize page loads (200 HTML); the old URL returned unknown_method.
    • oauth.v2.access accepts the app credentials (a dummy code gets invalid_code, not a client error).
    • A bot-token API call (auth.test) succeeds.
  • Live, Plaid (TypeScript SDK, sandbox): sandbox.plaid.com/oauth/token issues a Bearer token, with credentials in the body and no Authorization header. user:read, user:write and mcp:dashboard work; cra:report:read is "not allowed" for the test account.
  • Repo checks: sync_marketplace.py --check reports "In sync: 43 plugins, both registries, README.md, CLAUDE.md". check_plugin_versions.py reports plaid 0.2.0→0.2.1, slack 0.3.1→0.3.2, spotify 0.2.0→0.2.1. The diff is identical with and without --ignore-cr-at-eol.

Also in this regeneration

The newer plugin generator adds a .codex-plugin manifest, a scoped/ planner agent and a typescript-event-streams skill to each plugin. Tesla's plugin already has this layout. Manifests are rewritten to the marketplace conventions (APIMatic author, homepage, repository), and the generator's local-install README section is removed.

🤖 Generated with Claude Code

…ndpoints

Regenerates the three plugins against the SDKs just pushed, whose specs
now send OAuth to the right hosts:

- spotify: sign-in and tokens on accounts.spotify.com (previously built
  from api.spotify.com/v1, because the spec listed accounts.spotify.com
  as a second server/environment).
- slack: OAuth v2, authorize at slack.com/oauth/v2/authorize and the code
  exchange at slack.com/api/oauth.v2.access (previously the legacy
  oauth.access and a non-existent slack.com/api/authorize).
- plaid: tokens from /oauth/token on the selected environment, client
  credentials in the form body (previously api.plaid.com/oauth2/apiv2/token
  with HTTP Basic). Skills note that Plaid requires a scope.

The newer plugin generator also adds a .codex-plugin manifest, a scoped
planner agent and a typescript-event-streams skill. Versions: spotify
0.2.1, slack 0.3.2, plaid 0.2.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Darker98
Darker98 merged commit c8b2db1 into main Nov 16, 2026
2 checks passed
@Darker98
Darker98 deleted the fix-oauth-spotify-slack-plaid branch November 16, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant